Nathan Kopp wrote:
> 
> ...which is a big reason why I think POV needs post-processing built in.
> Actually, I think that POV should have post-processing utilities as part of
> the distribution, specifically designed to work with POV, though not part of
> the primary EXE.  Of course, in that case the IRTC rules would have to be be
> changed.
> 
> I don't know how to change the IRTC rules, but they currently seem to favor
> other rendering engines over POV (I'm talking about the official POV here,
> not MegaPov), and to me that seems a bit "backwards".

To me, the true spirit of that rule is that every effect should be
3D-related.  Applying gaussian blur all over, or manually, is not
3D-related.  But if the blur, even post-processed, uses 3D information
to know where and how it applies, it's fine.

That said, every embedded post-processing feature (including MegaPOV's)
also includes non-3D-related processes.  But excluding the use of these
for IRTC would require that every entrant (and voter) understands the 
difference between 3D-related and non-3D-related processing.  Given 
that 5% of them doesn't even understands what is a topic, such a rule
would be useless.

So, even if the current rule may sound somewhat stupid, it seems that
it does its job, avoiding the biggest mistakes.

Fabien.

Post a reply to this message